Validating transactions using information transmitted through magnetic fields

ABSTRACT

The technology described in this document can be embodied in a method that includes receiving, at one or more servers from a first computing device, (i) authentication information identifying a user-account associated with (a) the first computing device or (b) an application executing on the first computing device, and (ii) a transaction identifier generated by a second computing device. The transaction identifier is obtained by the first computing device by detecting one or more parameters of a magnetic field generated by the second computing device. The method also includes determining, by the one or more servers, that the user-account is authorized to initiate a transaction identified by the transaction identifier, and in response to determining that the user-account is authorized to initiate the transaction, transmitting, from the one or more servers to the second computing device, confirmation information usable by the second computing device to proceed with the transaction.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. patent application Ser. No.16/447,802, filed on Jun. 20, 2019, which is hereby incorporated byreference in its entirety.

TECHNICAL FIELD

This disclosure relates to methods and systems of processing financialtransactions by exchanging information over magnetic fields.

BACKGROUND

Financial transactions such as in-person purchases can be accomplishedusing various communication channels and mediums of exchange. Variousmethods of payment utilize the processing and sensing capabilities ofmobile computing devices to perform safe transactions.

SUMMARY

In one aspect, this document features a computer-implemented method thatincludes receiving, at one or more servers from a first computingdevice, (i) authentication information identifying a user-accountassociated with (a) the first computing device or (b) an applicationexecuting on the first computing device, and (ii) a transactionidentifier generated by a second computing device. The transactionidentifier is obtained by the first computing device by detecting one ormore parameters of a magnetic field generated by the second computingdevice. The method also includes determining, by the one or more serversbased on the authentication information, that the user-account isauthorized to initiate a transaction identified by the transactionidentifier, and in response to determining that the user-account isauthorized to initiate the transaction, transmitting, from the one ormore servers to the second computing device, confirmation informationusable by the second computing device to proceed with the transaction.

Implementations of the above aspect can include one or more of thefollowing features. The authentication information can be transmittedfrom the first computing device responsive to determining that a user ofthe first computing device is authorized to access the user-account. Thefirst computing device can be communicatively connected to a wearabledevice and the authentication information can be transmitted from thefirst computing device responsive to receiving a transactionconfirmation from the wearable device. The transaction identifier caninclude transaction information and an identifier of the secondcomputing device. The one or more parameters of the magnetic field caninclude at least one of a strength of the magnetic field and a directionof the magnetic field. The first computing device includes a receiverincluding a magnetic sensor configured to detect changes to the one ormore parameters of the magnetic field.

In another aspect, this document features a method of processing atransaction at a kiosk device. The method includes generating, by thekiosk device, a magnetic field to encode a transaction identifier. Themethod also includes receiving, from one or more servers by the kioskdevice, confirmation information identifying a mobile device thatdetects the transaction identifier generated by the kiosk device, andresponsive to receiving the confirmation information by the kioskdevice, proceeding with the transaction.

Implementations of the above aspect can include one or more of thefollowing features. The confirmation information can be transmitted fromthe one or more servers to the kiosk device responsive to receiving, bythe one or more servers from the mobile device: (i) authenticationinformation identifying a user-account associated with (a) the mobiledevice or (b) an application executing on the mobile device, and (ii) atransaction identifier generated by the kiosk device, wherein thetransaction identifier is obtained by the mobile device by detecting oneor more parameters of the magnetic field generated by the kiosk device.The authentication information can be transmitted from the mobile deviceto the one or more servers responsive to determining, by the mobiledevice, that a user of the mobile device is authorized to access theuser-account. The mobile device can be a wearable device communicativelyconnected to a second mobile device, and the confirmation informationcan be transmitted from the one or more servers to the kiosk deviceresponsive to receiving, by the one or more servers, the transactionidentifier from the second mobile device, where the transactionidentifier is transmitted from the second mobile device upon receivingthe transaction identifier from the wearable device. The transactionidentifier can include transaction information and an identifier of thekiosk device. Generating the magnetic field can include changing one ormore parameters of the magnetic field, the one or more parameters of themagnetic field including at least one of a strength of the magneticfield and a direction of the magnetic field. A receiver of the mobiledevice can include a magnetic sensor configured to detect the magneticfield to receive the transaction identifier.

In another aspect, this document features a system that includes atleast one processing device and a memory communicatively coupled to theat least one processing device. The memory stores instructions which,when executed, cause the at least one processing device to performoperations that include receiving, from a first computing device, (i)authentication information identifying a user-account associated with(a) the first computing device or (b) an application executing on thefirst computing device, and (ii) a transaction identifier generated by asecond computing device. The transaction identifier is obtained by thefirst computing device by detecting one or more parameters of a magneticfield generated by the second computing device. The operation alsoinclude determining, based on the authentication information, that theuser-account is authorized to initiate a transaction identified by thetransaction identifier, and in response to determining that theuser-account is authorized to initiate the transaction, transmitting, tothe second computing device, confirmation information usable by thesecond computing device to proceed with the transaction.

In another aspect, this document features a non-transitorycomputer-readable storage medium having encoded thereon computerreadable instructions for causing one or more processing devices toperform operations that include receiving, from a first computingdevice, (i) authentication information identifying a user-accountassociated with (a) the first computing device or (b) an applicationexecuting on the first computing device, and (ii) a transactionidentifier generated by a second computing device, wherein thetransaction identifier is obtained by the first computing device bydetecting one or more parameters of a magnetic field generated by thesecond computing device. The operation also include determining, basedon the authentication information, that the user-account is authorizedto initiate a transaction identified by the transaction identifier; andin response to determining that the user-account is authorized toinitiate the transaction, transmitting, to the second computing device,confirmation information usable by the second computing device toproceed with the transaction.

Implementations of the above aspects can include one or more of thefollowing features. The authentication information can be transmittedfrom the first computing device responsive to determining that a user ofthe first computing device is authorized to access the user-account. Thefirst computing device can be communicatively connected to a wearabledevice, where the authentication information is transmitted from thefirst computing device responsive to receiving a transactionconfirmation from the wearable device. The transaction identifier caninclude transaction information and an identifier of the secondcomputing device. The one or more parameters of the magnetic field caninclude at least one of a strength of the magnetic field and a directionof the magnetic field. The first computing device can include a receiverincluding a magnetic sensor configured to detect changes to the one ormore parameters of the magnetic field.

In another aspect, this document features a system that includes atleast one processing device and a memory communicatively coupled to theat least one processing device, the memory storing instructions which,when executed, cause the at least one processing device to performoperations for processing a transaction. The operations includegenerating a magnetic field to encode a transaction identifier. Theoperations also include receiving, from one or more servers,confirmation information identifying a mobile device that detects thetransaction identifier, and responsive to receiving the confirmationinformation, proceeding with the transaction.

In another aspect, this document features a non-transitorycomputer-readable storage medium that has encoded thereon computerreadable instructions for causing one or more processing devices toperform operations for processing a transaction. The operations includegenerating a magnetic field to encode a transaction identifier. Theoperations also include receiving, from one or more servers,confirmation information identifying a mobile device that detects thetransaction identifier, and responsive to receiving the confirmationinformation, proceeding with the transaction.

Implementations of the above aspects can include one or more of thefollowing features. The confirmation information can be transmitted fromthe one or more servers to the at least one processing device responsiveto receiving, by the one or more servers from the mobile device: (i)authentication information identifying a user-account associated with(a) the mobile device or (b) an application executing on the mobiledevice, and (ii) a transaction identifier generated by the at least oneprocessing device. The transaction identifier is obtained by the mobiledevice by detecting one or more parameters of the magnetic fieldgenerated by the at least one processing device. The authenticationinformation can be transmitted from the mobile device to the one or moreservers responsive to determining, by the mobile device, that a user ofthe mobile device is authorized to access the user-account. The mobiledevice can be a wearable device communicatively connected to a secondmobile device, where the confirmation information is transmitted fromthe one or more servers to the at least one processing device responsiveto receiving, by the one or more servers, the transaction identifierfrom the second mobile device, where the transaction identifier istransmitted from the second mobile device upon receiving the transactionidentifier from the wearable device. The transaction identifier caninclude transaction information and an identifier of a kiosk deviceassociated with the at least one processing device. Generating themagnetic field includes changing one or more parameters of the magneticfield. The one or more parameters of the magnetic field includes atleast one of a strength of the magnetic field and a direction of themagnetic field. A receiver of the mobile device can include a magneticsensor configured to detect the magnetic field to receive thetransaction identifier.

Various implementations described herein may provide one or more of thefollowing advantages. By using a magnetic signal to communicatetransaction information to a mobile device, transactions can beaccomplished without requiring significant affirmative actions by theuser with respect to a mobile device. Additionally, by using anear-field magnetic induction (NFMI) transmitter and leveraging thesensing capabilities of mobile devices, a communication channel betweenthe transmitter and mobile devices can be more secure than othertransaction systems. For example, the NFMI transmitter can form arelatively small ‘magnetic bubble’ that is immune from radio frequency(RF) interference and virtually secure from eavesdropping from outsidethat “bubble”. Additionally, the method described herein reduces theexchange of sensitive data by eliminating the need to transmit data fromthe mobile device to the kiosk device, reducing the risk of such databeing compromised.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A shows a kiosk machine as an example environment in which thetechnology described herein may be used.

FIG. 1B shows a schematic view of a transmitter module.

FIG. 2 depicts an example architecture in accordance withimplementations of the present disclosure.

FIG. 3 depicts an example timing diagram in accordance withimplementations of the present disclosure.

FIG. 4 is a flowchart of an example process for validating a transactionat a remote computing device.

FIG. 5 is a flowchart of an example process for facilitating atransaction at a kiosk device.

FIG. 6 is a block diagram representing examples of computing devices.

Repeat use of reference characters in the present specification anddrawings is intended to represent same or analogous features orelements.

DETAILED DESCRIPTION

This document presents technology for facilitating transactions betweentwo computing devices (e.g., a kiosk device and a mobile computingdevice) via exchange of information over a magnetic field between thetwo devices. In one example, a kiosk device transmits informationidentifying a transaction by modulating a magnetic field generated bythe kiosk. A mobile device present in the magnetic field can detect thechanges to the magnetic field (e.g., using a magnetic sensor such as amagnetometer) to receive the information, and provide it to a remoteserver (e.g., a server associated with a financial account of the user).Once the remote server determines that a user of the mobile device isauthorized to make the transaction, a transaction conformation is sentto the kiosk device, which proceeds with completing the transactionrequested by the user. Because the transaction information istransmitted from a first device (e.g., a kiosk) to a second device(e.g., a mobile device) over a magnetic field, no specific action may berequired on the part of a user of the mobile device to receive theinformation. For example, unlike what happens in a quick response (QR)code based transaction—where the user has to point a camera of a mobiledevice towards an image of a QR code to proceed with a transaction—theinformation can be transmitted to the mobile device as long as themobile device is within a detectable range of the magnetic field of thefirst device. This in turn can reduce user-actions required to process atransaction and provide an improved user experience. In fact, as long asthe user is authenticated (e.g., by way of a connected wearable devicesuch as a smart watch) to a corresponding mobile device, or a financialaccount accessible via the mobile device, a transaction can be completedeven without the user having to physically retrieve the mobile device.Also, because detectability of a magnetic field generated by aparticular device can be inversely proportional to a cube of thedistance from the device (the decay of the magnetic field may vary basedon the type of magnet used by the particular device), the technology canbe configured to allow transactions only when the two devices are withina low threshold distance (e.g., 2-3 feet) from one another. In somecases, this can ensure that the transaction is secure, and the transferof information is not intercepted by any malicious entity at arelatively remote location.

Various financial transactions occur in person, in which a purchaserpresents a financial institution card (e.g., credit card), a mobiledevice, a key fob, a smart card, or other forms of payment to completethe transaction. Some payment systems can leverage various communicationchannels to perform secure transactions including contactless payments.For example, some systems can leverage mobile devices and networkchannels to process safe transactions without swiping a card. Suchsystems can include the use of wireless communication methods such asnear field communication (NFC) protocols in which a mobile device or acard is placed near a card reader or an NFC reader to perform thetransaction. Such methods require the user to position the mobile devicenear the reader (e.g., within 0-2 inches) which can be inconvenient insome cases. Other systems include the use of encoded images (e.g., QRcodes or barcodes) to perform transactions. For example, a purchaser canuse a mobile device to scan a QR code to obtain the transactioninformation and send the information to a remote server to process apayment. However, the use of QR codes or barcodes also require multipleaffirmative actions by the user (e.g., pointing the camera towards thecode to capture an image etc.) to have the transaction processed.

The technology described herein facilitates processing of a transactionbetween two computing devices without requiring significant affirmativeactions by the user with respect to a mobile device. For example, when auser carrying a mobile device interacts with another device (e.g., akiosk device for ordering fast food), the corresponding transactioninformation (including identification information about the kiosk, theamount associated with the transaction, etc.) can be transferred to theuser's mobile device (as long it is within the vicinity) via magneticinduction, without the user having to even retrieve the mobile device.As long as the user is authenticated to the device (and/or any financialaccount accessible through the device), the transaction information canbe provided to a remote server for payment processing substantiallyautomatically. For example, if the user is wearing a connected wearabledevice such as a smartwatch, the user may be automatically authenticatedto the mobile device and/or the financial accounts accessible via themobile device. In any case, the user may have to at most provide someauthentication information via the connected wearable device or themobile device itself for the transaction to proceed. As such, thetechnology described herein facilitates a seamless user-experience wherethe number of affirmative actions performed by the user on the mobiledevice is low.

In one representative example, when a user attempts to perform atransaction at a secured device (e.g., a kiosk device), the secureddevice transmits a magnetic signal (e.g., a frequency encoded bitstring) using an electromagnet, wherein the magnetic signal is encodedwith a transaction identifier that includes the transaction informationand an identifier of the secured device. The magnetic signal can betransmitted, for example, by changing the magnetization of a magneticmaterial (e.g., by changing one or more parameters of a current flowingthrough a conductor around a ferromagnetic material core), which in turnchanges one or more parameters (e.g., a direction and/or strength) ofthe corresponding magnetic field. A mobile device (e.g., a smartphone ora smartwatch) in magnetic communication with the secured device (e.g.the kiosk) detects the signal from the secured device using a magneticsensor (e.g., a magnetometer configured to detect the changes whenplaced in the magnetic field). The mobile device then sends, after theuser associated with the corresponding mobile device has beenauthenticated by the mobile device, (i) the transaction identifier and(ii) authentication information (e.g., information identifying auser-account associated with [a] the mobile device or [b] an applicationexecuting on the mobile device) to a remote back-end system implemented,for example, on a server. In some examples, the information identifyingthe user-account includes an account number and a mobile deviceidentifier (e.g., the phone number of the mobile device) linked to theaccount number. In response, the server sends confirmation information(e.g., a confirmation that the user has been authenticated/verified andthat the transaction has been approved) to the secured device. Uponreceiving the confirmation information from the server, the secureddevice proceeds with the transaction. Upon verification andconfirmation, the payment may be automatically deducted from theuser-account or an account linked to the user-account to complete thetransaction.

In the example of a kiosk device, the device can have one or moreelectromagnets or transmitting coils positioned close to where the userstands to interact with the kiosk device. Such an arrangement caninclude a near field magnetic induction (NFMI) transmitter module. SuchNFMI transmitter can be activated using a proximity signal from a sensor(e.g., a proximity sensor) connected to the kiosk device such that theNFMI transmitter is triggered only when a user (along with his or herdevice) is within range to receive a magnetic signal encoded with theidentifier of the kiosk device. These proximity sensors can includesimple IR or ultrasonic proximity sensors, vision based proximitysensors, or pressure-sensing ground plates etc. In some implementations,the NFMI transmitter may have multiple coil systems for different zonesand activate its coils only in the zone(s) where user presence isdetected by the aforementioned proximity sensors. Such NFMI transmittercan generate a magnetic field detectable by the mobile device disposedwithin a limited vicinity (e.g., 0 to 36 inches) of the transmitter.Such system may improve the user experience by increasing the speed andaccuracy of authentication and can also add a security layer toadditional biometric authentication methods by including a second factor(user's trusted device) in the authentication loop.

The magnetic field generated by the NFMI transmitter can establish acommunication channel with the mobile device that is more secure thanother systems. For example, a concern with contactless payments is thatof eavesdropping. Eavesdropping occurs when a third party intercepts thesignal sent between two devices. If the third party intercepted a datatransmission between a smartphone and a credit card reader, the thirdparty can have access to sensitive information such as credit cardinformation. Eavesdropping can be a security concern for technologiessuch as QR, NFC, RFID, Bluetooth, and others since all of these caneither be visually observed (QR code) or electronically sensed at adistance much further away from the “transponder” than the actualcustomer position (i.e. Bluetooth transmits it's signal 30 feet ormore). However, the NFMI transmitter creates a relatively small‘magnetic bubble’ that is immune from radio frequency (RF) interferenceand virtually secure from eavesdropping from outside that “bubble”. Aneavesdropper would have to be standing next to the NFMI transmitter,within the magnetic bubble, to intercept wireless transmissions betweenthe NFMI transmitter and the mobile device. Additionally, the methoddescribed herein reduces the exchange of sensitive data by eliminatingthe need to transmit data from the mobile device to the kiosk device,reducing the risk of such data being compromised. Further, there is no“customer” data (i.e. identifier, account information, etc.) exchangedfrom the mobile device to the kiosk. Thus there is no sensitive datafrom the end customer available to “hack” even if the magnetic field is“read”. The information is flowing “one-way” from the kiosk to themobile device (kiosk device, purchase amount, etc.). The system thenaccomplishes the payment through alternative communication (through themobile device's standard, much more secure, connection to theapplication servers).

FIG. 1A shows a kiosk machine 100 as an example environment in which thetechnology described herein may be used. Such kiosk machines may be usedfor various purposes such as processing a transaction. For example, thekiosk 100 can include an ATM that allows a user to withdraw money from abank account. In another example, the kiosk 100 may be deployed at arestaurant or a fast-food outlet, and allow a user to order and pay forfood. The kiosk 100 may also be deployed at an entry point (e.g., at thegate of a store, an arena, or a stadium) to charge entrants prior toentering the venue. In general, the kiosk 100 may be deployed at varioustypes of locations to process transactions interactively. Additionally,the technology described herein may be deployed on a differentenvironment in which an NFMI transmitter can be implemented, such asrental bicycles or scooters or other related environments; includingreplacing QR codes in places where a mobile device is used to scan andreceive visible and unprotected information.

The kiosk 100 is configured to process a transaction by communicating atransaction identifier to the mobile device and receiving confirmationfrom a server system. For example, the kiosk 100 may include a displaydevice 110 (e.g., a capacitive touch screen) that allows a user 130 toselect and order food at a retail outlet. Once the user completes theselection via user-interface presented on the display device 110, thekiosk 100 can send a transaction identifier via a magnetic field to amobile device 150 of the user 130. Upon detecting or receiving thetransaction identifier, the mobile device can be prompted to verify thatthe user 130 is associated with a user account of the mobile device. Forexample, the mobile device can have software (e.g., a mobileapplication) that prompts the user, upon receiving the transactionidentifier from the NFMI transmitter, to perform an authentication step.For example, the mobile device 150 can include one or more componentsthat support a biometric authentication system such as a camera or afingerprint sensor that captures biometric information from the user(e.g., images of the user interacting with the mobile device). Thecaptured biometric information may be processed using an underlyingbiometric authentication system (e.g., using facial recognition or irisrecognition) to identify/authenticate the user as an authorized user ofa user-account associated with the mobile device. In someimplementations, the mobile device 150 can instead or in addition promptthe user to enter credentials associated with a user-account of themobile device to authenticate the user. In some implementations, themobile device may authenticate the user before the magnetic signal issent to the mobile device (e.g., the user has previously logged in tothe mobile application and remains logged in), in which cases the mobiledevice may prompt the user to simply confirm the purchase or evenproceed with the transaction without user confirmation. As furtherexplained in detail with respect to FIG. 2, after the user has beenauthenticated/verified, the mobile device 150 or a server system incommunication with the mobile device 150 can send a confirmation to thekiosk device 100 to proceed with the transaction.

In some implementations, the kiosk 100 can authenticate the user orcomplete the authentication process. For example, the kiosk 100 caninclude one or more components that support a biometric authenticationsystem such as an illumination source 115 and a camera 105 that capturesimages of users interacting with the kiosk 100. The captured images maybe processed using an underlying biometric authentication system toidentify/authenticate the user. For example, a server system can sendidentification information (e.g., previously enrolled biometrictemplates) pertaining to the user to the kiosk device 100. The kiosk 100can then compare the independently obtained information with theidentification information received from the server, and verify that theuser attempting to perform a transaction is the same user who isassociated with the mobile device.

Referring to FIGS. 1A and 1B, the kiosk 100 includes a transmittermodule 120 such as an electromagnet. The transmitter module 120transmits the transaction information and a kiosk identifier to themobile device 150 of a user 130 standing in front of or near the kiosk.FIG. 1B shows an example of an electromagnet that includes a conductor160 (e.g., a magnetic coil) wound around a magnetic core 170. Theconductor 160 is electrically coupled to an electric circuit 180 thatincludes a power source. The electric circuit 180 controls the electriccurrent sent through the conductor to control the magnetic field of theelectromagnet. For example, the magnetic field is generated by changingone or more parameters of a current (e.g., increasing and decreasing thecurrent or changing the direction of the current) flowing through theconductor 160 around the magnetic core 170 disposed at the kiosk 100.The electric circuit 180 can facilitate wireless transmission of theencoded data (e.g., a transaction identifier and a kiosk identifier)using a current that changes one or more parameters of a correspondingmagnetic field (e.g., changing the strength and direction of themagnetic field) as the current passes through the wound coil 160. Thestrength of the magnetic field can be measured as a magnetic fluxdensity. In some implementations, the electromagnet can be part of anNFMI communication system in which the electromagnet is configured togenerate a magnetic field that includes an NFMI signal.

In some implementations there are up to three magnetic coils 160 in thetransmitter module, along perpendicular axes, to encode the data pointsin a 3 dimensional vector space to improve data transmission quality andrate. To calibrate the receiver's orientation with that of this threedimensional NFMI transmitter to correctly decipher the transmitted datapoints in three dimensional magnetic coordinate system, the transmitter(e.g. kiosk) will send a predetermined handshake signal declaring its x,y, and z axes directions in certain order (e.g. sending a maximallycorrelational code such as a Barker sequence alongside x, then, y, andfinally z direction), and then the receiver (e.g., the mobile device150) will calibrate its orientation and find the spatial rotation matrixbetween transmitter and receiver given the received sequence andcomparing it to the expected transmitted sequence. In other words, toincrease the effectiveness of the mobile device 150 in picking up thesignal, the mobile device 150 can consider and use the most likelyorientation of the sensor axis with respect to the magnetic signal thatis most likely to receive a strong signal for decoding the magneticsignal. For example, an energy of target frequencies along with theexpected duration of the signal can be used to judge which sensor axesto include in the decoding process. In some implementations, incoherentdetection or short-term Fourier transform is used to detect thefrequency-coded information or symbols (FSK or m-FSK). Other frequencydetection processes, such as ones employing a Goertzel algorithm, canalso be used. In some implementations, the magnetic signal informationis encoded into the onsets of maximally correlated codes such as Barkersequences or chirps. In some implementations, the transmitter can sendFSK signals to the mobile device at a frequency up to half of themagnetometer sensors' sampling rate (typically 100 Hz) at speeds of upto 20 bits per second.

As shown in FIG. 1A, the user 130 has a mobile device 150 such as asmartphone. The mobile device includes any computing device that can becarried or worn by user 130, such as a smartphone, tablets, a PersonalDigital Assistant (PDAs), a smartwatch, and so forth. The mobile device150 can have decoding software configured to decode the change to theone or more parameters of the magnetic field. For example, the mobiledevice 150 may be programmed (e.g., through an installed application) todetect, decode, and send the magnetic signal (or its decoded informationsuch as the transaction identifier) transmitted via the transmitter 120.For example, mobile device 150 can be a smartphone that has a receiver(not shown) for receiving the magnetic signal. The receiver of themobile device 150 detects the parameter changes of the magnetic field orthe magnetic oscillations produced by the electromagnet (FIG. 1B). Insome implementations, detecting the changes to the parameters includesdetecting a frequency at which the one or more parameters change. Suchreceiver can include one or more magnetic sensors such as amagnetometer, a Hall Effect sensor, or a compass and decoding softwarethat, in combination with the sensors, receives the magnetic signal anddecodes the signal or detects the onset/preamble and transmits theensuing signal to a server or a third device for final processing anddecoding. As further discussed in detail with respect to FIG. 2, themobile device 150 sends a mobile device identifier and informationreceived from the magnetic signal to a server that then, based on thereceived information, sends a confirmation to the kiosk device 100 thatis used to complete the transaction, or to perform any other action thatmight be necessary based on detection of the presence of user's device(e.g., trusted device) in the vicinity of the transmitting kiosk. Insome implementations, the mobile device 150 is communicatively connectedto a wearable device 155 such as a smartwatch. The wearable device 155can have a receiver (not shown) such as a magnetic sensor for receivingthe transaction identifier sent by the kiosk. Upon detecting themagnetic signal, the wearable device 155 can prompt the user to confirmthe transaction. Upon receiving the confirmation from the user, thewearable device 155 can transmit the transaction identifier to themobile device 150, which can in turn authenticate the user and send theauthentication information and transaction identifier to the server. Insome implementations, the wearable device 155 can authenticate the userand communicate directly with the server. For example, the wearabledevice 155 can validate the user before receiving the magnetic signal.In some cases, the wearable device 155 can validate the user and remainin a ‘validated connected mode’ in which the user wears the wearabledevice and the wearable device is communicatively connected to themobile device 150. In such implementations, the wearable device 122 canreceive the transaction identifier from the kiosk 100 and send thetransaction identifier to the mobile device 150, which can in turn sendthe transaction identifier and the authentication information (e.g.,authentication information stored in the wearable device or in themobile device) to the server without requiring the user to interact withthe wearable device or the mobile device during the transaction.

In some implementations, the mobile device 150 has a low-frequencyreceiver with a sampling rate of up to 100 Hz, usually in form ofmulti-axes magnetic sensor. In some implementations, aliasing can beused when decoding a higher frequency chip with a low-sampling ratereceiver. For example, magnetic signals with higher-than-sampling ratefrequencies (e.g., frequencies modulated using frequency-shift keying[FSK]), such as 140 Hz can be equivalent to 40 Hz at the receiver sideat 100 Hz sampling. The bit rate may be increased by using multifrequency-shift keying (m-FSK) modulation where m>2, e.g., by assigning00 to 35, 01 to 40, 10 to 45, and 11 to 50 Hz, besides shortening symbolduration. Typical symbol duration is 100-200 ms providing up to 20bits/sec using the above-mentioned values. In some implementations,higher frequency magnetic waves may be used for data transmission bytaking advantage of aliasing. In this implementation, one can increasethe transmission signal frequency by an integer multiple of the samplingfrequency. For instance, if the magnetic sensor's sampling frequency is100 Hz and the original 0/1 FSK symbol frequencies were set at 35 and 45Hz respectively, one can use new aliased transmitter frequencies of135/145 Hz or 235/245 Hz with the same effective (aliased) readout of35/45 Hz on the receiver side. In some implementations, a preamblemagnetic signal can be transmitted using the same or different frequencybands via a magnetic transmitter to indicate the start of thetransmission and synchronization for a data pulse train.

The kiosk device 100 may include a processing computer (not shown)communicatively coupled with the transmitter 120. The processingcomputer can process the transaction and generate a transactionidentifier. The transaction identifier can be a unique code such as atransaction code and can include transaction details (without includingsensitive customer information). For example, the transaction identifiercan include transaction information such as items, quantities, amounts,any applicable taxes, date, time, shipping costs, and the like. Thekiosk identifier can be a unique code that identifies the correspondingkiosk. The processing computer may encode the transaction identifier andthe kiosk identifier in a binary code. For example, the transactionidentifier and the kiosk identifier may be encoded via FSK or m-FSKmodulation. The computer may then send a data stream with the binarycode to the transmitter 120. The transmitter 120, upon receiving thebinary code, converts such code into magnetic changes that have afrequency associated with the binary code. For example, the transmittermay produce a different frequency for each bit of a binary code.

In some implementations, in order to improve accuracy or user experience(or both), one can use the time stamps of the transmitted signals fortransmitter station identification or disambiguation. Since thetransmitting stations and the receiving devices are both incommunication with the service provider's servers, the server can usethe time stamps of the transmitted signal(s) from broadcastingstation(s) (where the user triggered the proximity sensor and initiatedthe magnetic wave transmission) to match them with those received byuser device(s) with closest time stamp(s) or other temporal signaturessuch as pulse intervals, duration, and matching templates. In someimplementations, this information is auxiliary and used fordisambiguation (increasing signal entropy) in conjunction with othercodes such as Frequency-shift keying (FSK). For example, one or moremodulation techniques can be used to encode the binary data. Suchmodulation techniques include FSK, Phase-shift keying (PSK),Amplitude-shift keying (ASK), or other resilient codes, and perhaps witherror detection and maybe error correction. In some implementations, allthe information is encoded temporally using indicators such as onset,duration, and intervals of transmitted signal bursts. In such cases, onemay use signal compression techniques such as chirps, Barker codes, andpseudo-random sequences to create burst signals with higher signal tonoise ratio and temporal resolution for temporal signature encoding,while keeping the burst duration short enough for better userexperience.

As shown in FIG. 1A, the kiosk device 100 can additionally include awireless module 125 such as a Bluetooth module. The wireless module 125may, in addition to the transmitter 120, communicate wirelessly with theelectronic device 150 to send the kiosk identifier or other information.In some implementations, the wireless module 125 may be used to ‘awaken’the mobile device 150. For example, the decoding routine software (e.g.,a pre-installed mobile application) may be awakened by the Bluetoothbeacon (or another location-based service) so that the decoder of themobile device can be triggered only when the user 130 is in front of orfacing the kiosk device 100. Such feature can improve the security ofthe system, decrease power consumption of the mobile device and thekiosk device, and decrease false positives. Additionally, the wirelessmodule 125 or similar can increase the reliability of the biometricauthentication system described herein. For example, even if the mobiledevice 150 doesn't correctly decode or partially decodes the magneticsignal, the server or kiosk device 100 can combine the mobile deviceidentification information with identification information received bythe wireless module 125 (or similar) to identify the user 130.

Referring to FIG. 2, a transaction system leverages a mobile computingdevice 150, transmitters, sensors, and communication channels such asdata networks to process a transaction. For example, a user 130 standingin front of the kiosk 100 may perform a transaction using the mobiledevice 150 without having to scan a computer-readable code or having toposition the mobile device adjacent a cardless reader. In this example,a back-end system such as a server system 230 includes one or moreprocessing devices 232 and memories 234 that store informationassociated with user 130, such as facial images captured during anenrollment process or encrypted credentials. The mobile device 150 maybe programmed (e.g., through an installed application) to detect,decode, and send the information received as a magnetic signaltransmitted from the kiosk 100. The information encoded in the magneticsignal may include a transaction identifier and a kiosk identifier. Uponreceiving and decoding the magnetic signal, mobile device 150authenticates the user. For example, the mobile device 150 can determinethat the user 130 is authorized to access the user-account associatedwith the mobile device or an application of the mobile device. In someimplementations, the mobile device 150 can authenticate the user using abiometric authentication method, a password authentication method, or asimilar method. Upon verifying the user, the mobile device 150 sends,through a network 210, (1) authentication information which may includea confirmation that the user has been verified or partially verified(and in some cases can include biometric information gathered by themobile device), and (2) the transaction identifier (which may include akiosk identifier) to server 230. After receiving the information fromthe mobile device 150, the server 230 determines, based on theauthentication information, that the user-account is authorized toinitiate a transaction identified by the transaction identifier. Whenthe user has been verified or authenticated, the server sends aconfirmation to the kiosk device 100 that the user has been verified andthe kiosk 100 then completes the transaction.

In some implementations, the server 230 can authenticate the user. Forexample, the memory 234 or storage device of server 230 contains atemplate gallery of users previously enrolled. Using the mobile deviceidentifier, the server finds the template (e.g., facial images orfingerprint scans) associated with the mobile device identifier andcompares those templates to the biometric information gathered by themobile device during run-time to authenticate the user. In someimplementations in which the user is partially authenticated by themobile device 150, the server 230 can complete the authenticationprocess. For example, the mobile device 150 can process the biometricinformation and then send the biometric information to the server 230.Upon receiving the processed biometric information of the user 130, theserver 230 can determine that the user 130 is authorized to use theuser-account associated with mobile device.

FIG. 3 depicts a timing diagram 300 that shows examples of interactionsbetween devices, and/or back-end systems in accordance withimplementations of the present disclosure. The example timing diagram300 includes a second computing device 302 (e.g., the kiosk device ofFIG. 1), a first computing device 304 (e.g., the mobile device of FIG.1), and a back-end system implemented in a server 306 (e.g., the serverof FIG. 2). In some implementations, the server 306 can be associatedwith a mobile application installed in the first computing device 304(e.g., the server and the mobile application can be associated with thesame institution such as a third-party payment platform).

In some implementations, a user (e.g., the user of FIG. 1) uses thesecond computing device 302 to initiate a transaction. For example, theuser can use the second computing device 302 to select items to bepurchased from a retailer. When the user indicates to the secondcomputing device 302 that the transaction can be completed (e.g., theuser selects a checkout option), the second computing device 302generates a transaction identifier. At a time ‘T1’, the second computingdevice 302 communicates the transaction identifier 310 (which caninclude an identifier of the second computing device) to the firstcomputing device 304 using a magnetic signal. Upon receiving theinformation from the second computing device 302, the first computingdevice 304 confirms that the user in possession of the first computingdevice 304 is an authorized user of the user-account associated with thefirst computing device (e.g., an application deployed on the firstcomputing device 304 asks the user to perform anauthentication/verification step such as entering a password or scanninga fingerprint). In some implementations, the user may already beauthenticated (e.g., the user has already accessed the mobileapplication configured to process the transaction), and the firstcomputing device 304 can communicate with the server 306 withoutreceiving further instructions from the user. Upon verifying that theuser is an authorized user (and in some cases after receiving aconfirmation from the user to proceed with the transaction), the firstcomputing device 304, at a time ‘T2’, sends the authenticationinformation and at least part of the transaction identifier 312 to theserver 306.

To process the payment, the first computing device 304 or the server 306can automatically withdraw the amount from the user account or requestpayment authorization and execution from a financial institution linkedto the user-account. In some implementations, the server 306 can processthe authentication information to authenticate the user or to completethe authentication process. After receiving the information from thefirst computing device 304, the server 306, at a time ‘T3’, sendsconfirmation information 314 to the second computing device. To send theconfirmation information, the server 306 uses the transaction identifier(which includes the identifier of the second computing device) todetermine a location of the second computing device 302. Theconfirmation information may include a confirmation that the userinteracting with the second computing device has been verified. Theconfirmation information can also include the authentication informationassociated with the first computing device. Upon receiving theconfirmation information, the second computing device 302 can completethe transaction. In some optional implementations, upon receiving theinformation from the first computing device 304, the server 306 can sendconfirmation information 318 to the first computing device 304 for thefirst computing device to notify the user or the second computing device302 that the user has been verified and/or that the transaction has beencompleted. In some implementations, the server 306 can send theconfirmation information to both the first computing device and thesecond computing device. In some implementations, the second computingdevice 302, upon receiving the confirmation information from the server,can send confirmation information 322 to the first computing device 304that the user has been verified and/or that the transaction has beencompleted. In some implementations, the second computing device 302 canremain in communication with the first computing device 304 throughoutthe transaction process. For example, the second computing device 302can use a communication channel established between the first and secondcomputing device to first send the transaction identifier at T1 to thefirst computing device 304 and then send confirmation information to thefirst computing device 304 at a later time.

FIG. 4 is a flowchart of an example process 400 for performing atransaction. In some implementations, at least a portion of the process400 may be executed by one or more processing devices disposed withinone or more servers such as the server 230 described with reference toFIG. 2. Operations of the process 400 includes receiving from a firstcomputing device, (i) authentication information identifying auser-account associated with (a) the first computing device or (b) anapplication executing on the first computing device, and (ii) atransaction identifier generated by a second computing device, whereinthe transaction identifier is obtained by the first computing device bydetecting one or more parameters of a magnetic field generated by thesecond computing device (405). The second computing device may include akiosk device and the first computing device may include a mobilecomputing device. The transaction identifier may include transactioninformation and a kiosk identifier, and the authenticationidentification may include a confirmation that the user has beenidentified or biometric information of the user, and a phone number orapplication identifier of the mobile computing device. The one or moreparameters of the magnetic field can include a strength of the magneticfield and a direction of the magnetic field. The mobile computing deviceis considered to be in physical vicinity of the user (e.g. carried inpockets, a purse, or bag) to detect the kiosk-transmitted magneticsignal. The mobile computing device has a receiver that may include asensor configured to detect the magnetic signal and may additionallyinclude decoding software configured to decode the magnetic signal.

In some implementations, the authentication information can betransmitted from the first computing device responsive to determiningthat a user of the first computing device is authorized to access theuser-account. The first computing device can be communicativelyconnected to a wearable device, and the authentication information canbe transmitted from the first computing device responsive to receiving atransaction confirmation from the wearable device.

Operations of the process 400 further includes determining, by theserver based on the authentication information, that the user-account isauthorized to initiate a transaction identified by the transactionidentifier (410), and transmitting, from the server to the secondcomputing device confirmation information usable by the second computingdevice to proceed with the transaction (415).

FIG. 5 is a flowchart of an example process for facilitating atransaction. In some implementations, at least a portion of the process500 may be executed by one or more kiosk devices such as the kioskdevice 100 described with reference to FIG. 1A. Operations of theprocess 500 include generating, by the kiosk device, a magnetic field toencode a transaction identifier (502). The process 500 may, in addition,contain a proximity sensing mechanism, such as floor-embedded pressuresensors or other proximity sensors such as capacitive, infrared,ultrasonic, image based, or time of flight proximity sensors to initiatethe magnetic field or magnetic signal transmission only when the user isproperly standing in front of the kiosk. The process 500 furtherincludes receiving, from one or more servers by the kiosk device,confirmation information identifying a mobile device that detects thetransaction identifier generated by the kiosk device (504). Operationsof the process 500 further include, responsive to receiving theconfirmation information by the kiosk device, proceeding with thetransaction (506).

FIG. 6 shows an example of a computing device 600 and a mobile device650, which may be used with the techniques described here. For example,referring to FIG. 1, the kiosk device 100 can include one or more of thecomputing device 600 or the mobile device 650, either in part or in itsentirety. Computing device 5400 is intended to represent various formsof digital computers, such as laptops, desktops, workstations, personaldigital assistants, servers, blade servers, mainframes, and otherappropriate computers. Computing device 650 is intended to representvarious forms of mobile devices, such as personal digital assistants,cellular telephones, smartphones, and other similar computing devices.The components shown here, their connections and relationships, andtheir functions, are meant to be examples only, and are not meant tolimit implementations of the techniques described and/or claimed in thisdocument.

Computing device 600 includes a processor 602, memory 604, a storagedevice 606, a high-speed interface 608 connecting to memory 604 andhigh-speed expansion ports 610, and a low speed interface 612 connectingto low speed bus 614 and storage device 606. Each of the components 602,604, 606, 608, 610, and 612, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 602 can process instructions for executionwithin the computing device 600, including instructions stored in thememory 604 or on the storage device 606 to display graphical informationfor a GUI on an external input/output device, such as display 616coupled to high speed interface 608. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices600 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 604 stores information within the computing device 600. Inone implementation, the memory 604 is a volatile memory unit or units.In another implementation, the memory 604 is a non-volatile memory unitor units. The memory 604 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 606 is capable of providing mass storage for thecomputing device 600. In one implementation, the storage device 606 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 604, the storage device 606,memory on processor 602, or a propagated signal.

The high speed controller 608 manages bandwidth-intensive operations forthe computing device 600, while the low speed controller 612 manageslower bandwidth-intensive operations. Such allocation of functions is anexample only. In one implementation, the high-speed controller 608 iscoupled to memory 604, display 616 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 610, which may acceptvarious expansion cards (not shown). In the implementation, low-speedcontroller 612 is coupled to storage device 606 and low-speed expansionport 614. The low-speed expansion port, which may include variouscommunication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet)may be coupled to one or more input/output devices, such as a keyboard,a pointing device, a scanner, or a networking device such as a switch orrouter, e.g., through a network adapter.

The computing device 600 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 620, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 624. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 622. Alternatively, components from computing device 600 may becombined with other components in a mobile device (not shown), such asdevice 650. Each of such devices may contain one or more of computingdevice 600, 650, and an entire system may be made up of multiplecomputing devices 600, 650 communicating with each other.

Computing device 650 includes a processor 652, memory 664, aninput/output device such as a display 654, a communication interface666, and a transceiver 668, among other components. The device 650 mayalso be provided with a storage device, such as a microdrive or otherdevice, to provide additional storage. Each of the components 650, 652,664, 654, 666, and 668, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 652 can execute instructions within the computing device650, including instructions stored in the memory 664. The processor maybe implemented as a chipset of chips that include separate and multipleanalog and digital processors. The processor may provide, for example,for coordination of the other components of the device 650, such ascontrol of user interfaces, applications run by device 650, and wirelesscommunication by device 650.

Processor 652 may communicate with a user through control interface 658and display interface 656 coupled to a display 654. The display 654 maybe, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display)or an OLED (Organic Light Emitting Diode) display, or other appropriatedisplay technology. The display interface 656 may comprise appropriatecircuitry for driving the display 654 to present graphical and otherinformation to a user. The control interface 658 may receive commandsfrom a user and convert them for submission to the processor 652. Inaddition, an external interface 662 may be provide in communication withprocessor 652, so as to enable near area communication of device 650with other devices. External interface 662 may provide, for example, forwired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 664 stores information within the computing device 650. Thememory 664 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 674 may also be provided andconnected to device 650 through expansion interface 672, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 674 may provide extra storage space fordevice 650, or may also store applications or other information fordevice 650. Specifically, expansion memory 674 may include instructionsto carry out or supplement the processes described above, and mayinclude secure information also. Thus, for example, expansion memory 674may be provide as a security module for device 650, and may beprogrammed with instructions that permit secure use of device 650. Inaddition, secure applications may be provided via the SIMM cards, alongwith additional information, such as placing identifying information onthe SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 664, expansionmemory 674, memory on processor 652, or a propagated signal that may bereceived, for example, over transceiver 668 or external interface 662.

Device 650 may communicate wirelessly through communication interface666, which may include digital signal processing circuitry wherenecessary. Communication interface 666 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 668. In addition, short-range communication may occur, suchas using a Bluetooth, WiFi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 670 mayprovide additional navigation- and location-related wireless data todevice 650, which may be used as appropriate by applications running ondevice 650.

Device 650 may also communicate audibly using audio codec 660, which mayreceive spoken information from a user and convert it to usable digitalinformation. Audio codec 660 may likewise generate audible sound for auser, such as through a speaker, e.g., in a handset of device 650. Suchsound may include sound from voice telephone calls, may include recordedsound (e.g., voice messages, music files, and so forth) and may alsoinclude sound generated by applications operating on device 650.

The computing device 650 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 680. It may also be implemented as part of asmartphone 682, personal digital assistant, tablet computer, or othersimilar mobile device.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well. For example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback). Input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

Although a few implementations have been described in detail above,other modifications may be made without departing from the scope of theinventive concepts described herein, and, accordingly, otherimplementations are within the scope of the following claims.

What is claimed is:
 1. A method of processing a transaction at a kioskdevice, the method comprising: transmitting, by the kiosk device to amobile device, a handshake signal i) that identifies directions of axesof a three dimensional coordinate system and ii) is usable by the mobiledevice to calibrate an orientation of the mobile device based on thedirections of the axes of the three dimensional coordinate system;generating, by the kiosk device, a magnetic field to encode atransaction identifier in the three dimensional coordinate system;receiving, from one or more servers by the kiosk device, confirmationinformation of a user account associated with the mobile device thatdetects, based on a calibrated orientation determined from the handshakesignal, the transaction identifier generated by the kiosk device; andresponsive to receiving the confirmation information by the kioskdevice, proceeding with the transaction.
 2. The method of claim 1,wherein the confirmation information is transmitted from the one or moreservers to the kiosk device responsive to receiving, by the one or moreservers from the mobile device: (i) authentication informationidentifying a user-account associated with (a) the mobile device or (b)an application executing on the mobile device, and (ii) the transactionidentifier generated by the kiosk device, wherein the transactionidentifier is obtained by the mobile device by detecting one or moreparameters of the magnetic field generated by the kiosk device.
 3. Themethod of claim 2, wherein the authentication information is transmittedfrom the mobile device to the one or more servers responsive todetermining, by the mobile device, that a user of the mobile device isauthorized to access the user-account.
 4. The method of claim 1, whereina wearable device is communicatively connected to the mobile device, andwherein the confirmation information is transmitted from the one or moreservers to the kiosk device responsive to receiving, by the one or moreservers, the transaction identifier from the mobile device, thetransaction identifier transmitted from the mobile device upon receivingthe transaction identifier from the wearable device.
 5. The method ofclaim 1, wherein the transaction identifier comprises transactioninformation and an identifier of the kiosk device.
 6. The method ofclaim 1, wherein generating the magnetic field comprises changing one ormore parameters of the magnetic field, the one or more parameters of themagnetic field comprising at least one of a strength of the magneticfield and a direction of the magnetic field.
 7. The method of claim 1,wherein a receiver of the mobile device comprises a magnetic sensorconfigured to detect the magnetic field to receive the transactionidentifier.
 8. A system comprising: at least one processing device; anda memory communicatively coupled to the at least one processing device,the memory storing instructions which, when executed, cause the at leastone processing device to perform operations for processing atransaction, the operations comprising: transmitting, to a mobiledevice, a handshake signal i) that identifies directions of axes of athree dimensional coordinate system and ii) is usable by the mobiledevice to calibrate an orientation of the mobile device based on thedirections of the axes of the three dimensional coordinate system;generating a magnetic field to encode a transaction identifier in thethree dimensional coordinate system; receiving, from one or moreservers, confirmation information of a user account associated with themobile device that detects, based on a calibrated orientation determinedfrom the handshake signal, the transaction identifier generated by akiosk device; and responsive to receiving the confirmation information,proceeding with the transaction.
 9. The system of claim 8, wherein theconfirmation information is transmitted from the one or more servers tothe at least one processing device responsive to receiving, by the oneor more servers from the mobile device: (i) authentication informationidentifying a user-account associated with (a) the mobile device or (b)an application executing on the mobile device, and (ii) the transactionidentifier generated by the at least one processing device, wherein thetransaction identifier is obtained by the mobile device by detecting oneor more parameters of the magnetic field generated by the at least oneprocessing device.
 10. The system of claim 9, wherein the authenticationinformation is transmitted from the mobile device to the one or moreservers responsive to determining, by the mobile device, that a user ofthe mobile device is authorized to access the user-account.
 11. Thesystem of claim 8, wherein a wearable device is communicativelyconnected to the mobile device, and wherein the confirmation informationis transmitted from the one or more servers to the kiosk deviceresponsive to receiving, by the one or more servers, the transactionidentifier from the mobile device, the transaction identifiertransmitted from the mobile device upon receiving the transactionidentifier from the wearable device.
 12. The system of claim 8, whereinthe transaction identifier comprises transaction information and anidentifier of the kiosk device associated with the at least oneprocessing device.
 13. The system of claim 8, wherein generating themagnetic field comprises changing one or more parameters of the magneticfield, the one or more parameters of the magnetic field comprising atleast one of a strength of the magnetic field and a direction of themagnetic field.
 14. The system of claim 8, wherein a receiver of themobile device comprises a magnetic sensor configured to detect themagnetic field to receive the transaction identifier.
 15. Anon-transitory computer-readable storage medium having encoded thereoncomputer readable instructions for causing one or more processingdevices to perform operations for processing a transaction, theoperations comprising: transmitting, to a mobile device, a handshakesignal i) that identifies directions of axes of a three dimensionalcoordinate system and ii) is usable by the mobile device to calibrate anorientation of the mobile device based on the directions of the axes ofthe three dimensional coordinate system; generating a magnetic field toencode a transaction identifier in the three dimensional coordinatesystem; receiving, from one or more servers, confirmation information ofa user account associated with the mobile device that detects, based ona calibrated orientation determined from the handshake signal, thetransaction identifier generated by a kiosk device; and responsive toreceiving the confirmation information, proceeding with the transaction.16. The non-transitory computer-readable storage medium of claim 15,wherein the confirmation information is transmitted from the one or moreservers to the one or more processing devices responsive to receiving,by the one or more servers from the mobile device: (i) authenticationinformation identifying a user-account associated with (a) the mobiledevice or (b) an application executing on the mobile device, and (ii)the transaction identifier generated by the one or more processingdevices, wherein the transaction identifier is obtained by the mobiledevice by detecting one or more parameters of the magnetic fieldgenerated by the one or more processing devices.
 17. The non-transitorycomputer-readable storage medium of claim 16, wherein the authenticationinformation is transmitted from the mobile device to the one or moreservers responsive to determining, by the mobile device, that a user ofthe mobile device is authorized to access the user-account.
 18. Thenon-transitory computer-readable storage medium of claim 15, a wearabledevice is communicatively connected to the mobile device, and whereinthe confirmation information is transmitted from the one or more serversto the kiosk device responsive to receiving, by the one or more servers,the transaction identifier from the mobile device, the transactionidentifier transmitted from the mobile device upon receiving thetransaction identifier from the wearable device.
 19. The non-transitorycomputer-readable storage medium of claim 15, wherein the transactionidentifier comprises transaction information and an identifier of thekiosk device associated with the one or more processing devices.
 20. Thenon-transitory computer-readable storage medium of claim 15, whereingenerating the magnetic field comprises changing one or more parametersof the magnetic field, the one or more parameters of the magnetic fieldcomprising at least one of a strength of the magnetic field and adirection of the magnetic field.
 21. The non-transitorycomputer-readable storage medium of claim 15, wherein a receiver of themobile device comprises a magnetic sensor configured to detect themagnetic field to receive the transaction identifier.